Skip to content

Conversation

@sg-doc-holiday
Copy link

@sg-doc-holiday sg-doc-holiday bot commented Jan 15, 2026

Release notes

  • Adds a new release notes page (release-notes.mdx) with front matter to be published by the documentation system
  • Injects detailed release notes for the 2026-01-15 release window covering new features, improvements, and bug fixes
  • Documents updates such as OpenOps Tables version bump, improved admin seeding, enhanced chat transcript reliability, Analytics page access protections, GPT-5.2 support in AI workflows, and ability to disable analytics service
  • Creates the release-notes.mdx page with initial detailed release notes content in JSON format within markdown
  • Updates the release notes entries to trim them to single sentences as per release notes workflow guidelines
  • Converts JSON structured release notes into markdown format with emoji-category headers and bulleted lists following the style guide
  • Adjusts release notes headings to use smaller heading levels below the date section, maintaining emoji category headers for improvements, fixes, and new features as per style guide

This covers 4 commits.

Interaction Instructions

This PR was generated by Doc Holiday and is ready to be iterated on.

Leave comments on this pull request in plain English to guide Doc Holiday's next steps.
You might ask to:

  • Update or rewrite documentation
  • Create or update release notes
  • Remove sections or files
  • Merge this PR with another Doc Holiday PR

Examples:

  • @doc.holiday update these docs to follow my style guide: https://link.to/style-guide
  • @doc.holiday write new documentation about quantum compute and how its steam generates a 429
  • @doc.holiday combine this PR with #404
  • @doc.holiday delete this file: release-notes/file.md

This was opened from: https://github.com/openops-cloud/openops/releases/tag/0.6.14

Add a release notes page and inject the latest calculated release notes for the 2026-01-15 release window (Event Time), using required front matter so it can be published by the documentation system.
Trim each newly added release note entry to a single sentence by keeping text up to the first final period, per release notes workflow step 4.
Convert interpolated JSON into the required release notes markdown structure with emoji category headers and '-' bullet items without periods at the end, per style guide.
Align release notes headings with style guide heading rules by using smaller category headings under the date section, while keeping emoji category headers and bullet formatting.
Reorder sections to match common/expected older release note conventions: new features first, then improvements, then fixes, while preserving emoji category headers and one-line bullet entries.
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant